Power management scheme for portable data collection devices utilizing location and position sensors

ABSTRACT

A data collection device (DCD) is placed in a first low power mode after the DCD has been in a first predetermined position, and placed in a second low power mode after a first predetermined period of time. In another embodiment the DCD includes a wireless telephone, and a proximity sensor which detects when the DCD is close to a user&#39;s face, wherein the telephone is automatically put in a handset mode when the DCD is close to a user&#39;s face, and automatically put in a speakerphone mode when the DCD is not close to a user&#39;s face.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims the benefit of U.S. patent applicationSer. No. 15/164,924 for a Power Management Scheme for Portable DataCollection Devices Utilizing Location and Position Sensors filed May 26,2016 (and published Sep. 15, 2016 as U.S. Patent Publication No.2016/0269997), now U.S. Pat. No. 9,615,331, which claims the benefit ofU.S. patent application Ser. No. 14/831,938 for a Power ManagementScheme for Portable Data Collection Devices Utilizing Location andPosition Sensors filed Aug. 21, 2015 (and published Dec. 24, 2015 asU.S. Patent Publication No. 2015/0373647), now U.S. Pat. No. 9,357,494,which claims the benefit of U.S. patent application Ser. No. 14/082,551for a Power Management Scheme for Portable Data Collection DevicesUtilizing Location and Position Sensors filed Nov. 18, 2013 (andpublished Mar. 6, 2014 as U.S. Patent Application Publication No.2014/0066136), now U.S. Pat. No. 9,119,155, which claims the benefit ofU.S. patent application Ser. No. 12/689,521 for a Power ManagementScheme for Portable Data Collection Devices Utilizing Location andPosition Sensors filed Jan. 19, 2010 (and published Jul. 21, 2011 asU.S. Patent Application Publication No. 2011/0177846), now U.S. Pat. No.8,588,869. Each of the foregoing patent applications, patentpublications, and patents is hereby incorporated by reference in itsentirety.

FIELD OF THE INVENTION

This invention relates to the management of remote devices such asportable data terminals (PDTs), and more particularly to an interfacefor managing the remote devices.

BACKGROUND

Optimizing power management to maximize the available energy budget inportable data terminal is a constant struggle. Due to an increasedperipheral set, ruggedized portable data terminals are particularlyproblematic with respect to power management issues. It is desirable toput the portable data terminal into a low power state whenever theoperator is not actively using the device. Many systems implement timebased inactivity determination. However, time based systems are muchless efficient at managing energy consumption.

The remote devices can have the ability to have their configurationchanged or to have a new application program installed while away fromthe central office. U.S. Patent Publication No. 2009/0044003 A1 toBerthiaume et al. teaches such a method, and is hereby incorporated byreference.

The remote devices can be managed by Remote Device Management (RDM)systems that allow an RDM user to manage the remote devices includingupdating configurations and device software, and to track problems whichmay be common to several devices, and provide fixes for these problemswhere feasible.

However, some RDM systems accumulate vast amounts of diagnostic andperformance data. Organizing the data in a clear, concise, meaningful,and intuitive way on the graphical user interface of a computer displayis a problem. Either too much data is presented so as to be clutteredand confusing, or the user has to navigate through multiple, sometimesnon-intuitive, dialogs to access desired information.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a front view of a data collection device (DCD) according toone embodiment of the present invention;

FIG. 2 is a block diagram of the DCD shown in FIG. 1;

FIGS. 3A, 3B, and 3C are flow charts according to an embodiment of aprocess for power management which may be used in the DCD shown in FIG.1;

FIG. 4 is a flow chart according to another embodiment of a process forpower management which may be used with the DCD shown in FIG. 1;

FIG. 5 is a side view of a DCD according to another embodiment of thepresent invention; and

FIG. 6 is a flow chart according to an embodiment of a process for powermanagement which may be used with the DCD shown in FIG. 5.

It will be appreciated that for purposes of clarity and where deemedappropriate, reference numerals have been repeated in the figures toindicate corresponding features. Also, the relative size of variousobjects in the drawings has in some cases been distorted to more clearlyshow the invention.

DETAILED DESCRIPTION

Turning now to the drawings, FIG. 1 shows a data collection device (DCD)10, which may be a Personal Digital Assistant (PDA), according to oneembodiment of the present invention. The DCD 10 has a main body 12 withan antenna 14 attached to the main body 12. A keypad 16 is located inthe lower portion of the DCD 10, and a display 18 is located in an upperportion of the DCD 10. A touch sensitive panel 20 is superimposed on thedisplay 18 for allowing a user to select options on the displaydirectly.

Located above the display 18 is a combination ambient light sensor andproximity sensor 22, which may include a LED 24, a combinationphotodiode array and optical filter 26 to detect the amount of ambientlight in the wavelengths detected by the human eye, and a secondcombination photodiode array and optical filter 28 to detect the amountof light in the infrared range which is used for proximity detection.Located slightly above and to the right of the combination ambient lightsensor and proximity sensor 22 is a handset speaker 30 (shown in FIG. 2)located behind six holes 32. The keypad 16 includes a scan key 34 foractivating a bar code scanner built into the DCD 10. The keypad 16 alsoincludes a send key 38 which may be used to begin a conversation with awireless telephone built into the DCD 10. Also shown in FIG. 1 is athree axis diagram 40 indicating the orientation of a three axisaccelerometer 42 (shown in FIG. 2) built into the DCD 10.

FIG. 2 is a block diagram 48 of the DCD 10 shown in FIG. 1. Those ofordinary skill in the art will recognize that the illustrated design ofthe DCD 10 has been simplified so as to permit a briefer explanation ofsystems and components not directly related to the present invention.

A central processing unit (CPU) 50 receives data from and outputs datato other sub-systems for storage, transmission and additionalprocessing. CPU 50 may be implemented using any number of off the shelfsolutions including: embedded processors; general purpose processors;any number of RISC processors; or any number of custom solutionsincluding pre-configured floating point gate arrays (FPGAs); andapplication specific integrated circuits (ASICs). Overall operation ofthe CPU 50 is controlled by software or firmware, typically referred toas an operating system which may be stored in one or more memorylocations 52 n, including RAM 52 a and FLASH memory 52 b. Examples ofsuitable operating systems for DCD 10 include SYMBIAN: WINDOWS MOBIL,WINDOWS CE, WINDOWS XP, LINUX, PALM, and OSX.

In general, communication to and from the CPU 50 and among the varioussub-components takes place via one or more ports or busses, including amain system bus 54, and I²C bus 56; a plurality of UniversalAsynchronous Receivers/Transmitter (UART) ports 58 n, Universal SerialBusses (USB) 60 n, and a RS-232 port 62.

The illustrated CPU 50 is coupled to the display 18 through a LCDcontroller 63 and to the touch sensitive panel 20 which has anintegrated controller 64. The combination of the display 18 and thetouch sensitive panel 20 is often referred to as a “touch screen.” Thetouch sensitive panel 20 may be in communication with the CPU 50 and anauxiliary processor 66 via the I²C bus 56.

The DCD 10 may further include a plurality of wireless communicationlinks such as an 802.11 communication link 68, an 802.16 communicationlink 70, a communication link 72 for telephone (phone) communicationwith a cellular network such as a network in accordance with the GlobalSystem for Mobile Communications (GSM) or one that conforms to the CodeDivision Multiple Access (CDMA) standard, an IR communication link 74,and/or a Bluetooth communication link 76. Each of these linksfacilitates communication with a remote device and may be used totransfer and receive data. Other possible links include: an 802.15.4link, a UMTS link, and a HSPDA link.

A variety of secondary processors may be provided to perform general andapplication specific functions. The example illustrated in FIG. 2provides two such processors: a field programmable gate array (FPGA) 80and the auxiliary processor 66. The FPGA 80 may comprise any of a numberof FPGAs including the Virtex-4 family of FPGAs available from XILINX.The auxiliary processor 66 may comprise any of a number of embedded (orgeneral purpose) processors, including one of the AVR RISC processorsavailable from ATMEL CORPORATION.

The auxiliary processor 66 may interface with a variety of data inputdevices including, for example, the keypad 16 and the scan key 34. Byway of example, the DCD 10 may be configured so that displayed menuoptions are selected by physically depressing a key on the keypad 16 oractivating the touch screen 20 with use of a finger or stylus. The scankey 34 may be used for initiating and controlling one or more datacollection systems, such as an image signal generating system 82.Although not shown in FIG. 2, the DCD 10 may also contain an RFIDsensing system and a magnetic strip reader which may be initiated withthe scan key 34.

The data collection system (e.g. the image signal generating system 82)may be controlled by the FPGA 80. In this case, the FPGA 80 initiatesand controls the operation of the data collection systems andaccumulates data received there from prior to depositing such data inmemory 52 n. Possible configurations of FPGA 80 are illustrated in U.S.Pat. No. 6,947,612 incorporated herein by reference. The image signalgenerating system 82 generally comprises a solid state image sensor 84useful for imaging bar code 86 on a package 88.

The three axis accelerometer 42 and the ambient light and proximitysensors 22 are coupled to the main system bus 54. The three axisaccelerometer may be made by Analog Devices, and the combination ambientlight sensor and proximity sensor made by Intersil Corp. The DCD 10 mayinclude a keypad light 90 used to illuminate the keypad 16. An audioprocessing circuit 92, connected to the main system bus 54, drives aspeaker 94, located on the back of the DCD 10, used when the DCD 10 isin a speakerphone or hands free mode, the handset speaker 30, and amicrophone 96 which may be located on a side of the DCD 10.

A power circuit 100 is supplied for the controlling supplying of powerto the DCD 10. The power circuit 100 generally comprises a series ofpower supplies 102 n that regulate the power supplied to the variouscomponents of the DCD 10. Each power supply 102 n generally comprises astep up or step down circuit connected to each of the various componentsin the DCD 10 that require the particular voltage output by that powersupply 102 n. In particular, the CPU 50 receives power form a powersupply 102 d, the display 18 receives power from the power supply 102 b,the touch sensitive panel 20 receives power from the power supply 102 a,and the keypad light 90 receives power from a power supply 102 e.Although separate power supplies, 102 a, 102 b, and 102 e, are shown toprovide power to the touch sensitive panel 20, the display 18, and thekeypad light 90, respectively, two or more of these power supplies maybe combined and drive two or more of these components.

The power supplies 102 n receive electricity from a power bus 103 whichis, in turn, supplied by a battery 104 or may be supplied by a secondpower input on the connector 106. A connector 106 may comprise anynumber of known connection technologies, such as the D (or sub-D) Seriesof circular plastic connectors or the HCL D-sub derivative design datatransfer connector. Certain pins of the connector 106 may be dedicatedto receiving DC power, while other pins are dedicated to one or morecommunication paths, e.g. RS-232 and USB. It may also prove advantageousto provide DC power out, for example from a power supply 102 c, so as topower tethered accessories, such as external magnetic stripe or RFIDreaders (not shown).

The battery 104 may be selected from any of a variety of batterytechnologies including fuel cell, NiMh, NiCd, Li Ion, or Li Polymer. Thebattery 104 is charged by a charge circuit 110 which receives power fromthe connector 106. The charge circuit 110 may comprise any of a numberof available circuits.

A switch 112 isolates the battery based upon the presence of power fromthe connector 106. Thus, when an external power supply is connected tothe connector 106, the switch 112 is opened and the battery is isolatedfrom the power supplies 102 n and may be charged via the charge circuit110. Once power is removed from the connector 106, the battery isconnected to the power supplies 102 n.

The power consumption of any system in a sleep state may vary based onthe system and sleep routines associated therewith. For example, a CPUmay have a plurality of sleep states each of which has a different powerprofile and active functions. Accordingly, as used herein, the termsleep state will generally refer to a state in which one or morecomponents or functions of a system or sub-subsystem are inactivated orlimited in a manner known in the art by software in the CPU 50 so as toreduce power consumption.

FIGS. 3A, 3B, and 3C are flow charts according to one embodiment of aprocess for power management which may be used in the DCD shown inFIG. 1. Beginning at letter A in FIG. 3A, with timers T1, T2, and T3 setto zero, the three axis accelerometer 42 detects if the DCD 10 has beenput front down in decision block 130. The term “front down” means thatthe three axis accelerometer detects the earth's gravity in the positiveZ direction indicated in FIG. 1, and essentially no pull of gravity ineither the X or Y directions. If the DCD 10 is not front down, then theflow chart of FIG. 3A branches to letter B which continues in FIG. 3B.If the DCD 10 is lying front down then, because the display 18 andkeypad 16 are not in use, the display 18, touch sensitive panel 20 andkeypad light 90 are turned off to put the DCD 10 into a first sleepstate as shown in block 132. There may be a short delay before the firstsleep state is activated after the DCD 10 is turned front down to avoidentering a low power state inadvertently. Then a first timer T1 isstarted as shown in block 134. The timer T1 may be implemented bystarting the timer with a predetermined time, and once started,decremented until the timer T1 times out by reaching zero. After thetimer T1 has started the three axis accelerometer 42, the keypad 16, andthe phone in the DCD 10 are monitored to detect if the DCD 10 is moving,whether a key on the keypad 16 is depressed, or whether the phone in theDCD is in use in decision block 136. If none of these events hasoccurred, then the timer T1 is checked to see if it has timed out indecision block 138. If not then the state of the DCD 10 passes to thedecision block 136. Thus the three axis accelerometer 42, the keypad 16,and the phone in the DCD 10 are monitored to detect if the DCD 10 ismoving, whether a key on the keypad 16 is depressed, or whether thephone in the DCD is in use during the time that the timer T1 isoperating.

If, during the period of time that the DCD 10 is monitoring the threeaxis accelerometer 42, the keypad 16, and the use of the phone in theDCD 10 in decision block 136, if the DCD 10 is moved, a key on thekeypad 16 is depressed, or the phone in the DCD is in use, then timer T1is reset in block 140, and the state of the DCD 10 passes from block 140to decision block 130.

If the timer T1 has timed out in decision block 138, then the DCD 10will enter sleep state 2 as indicated in block 142. Once the DCD 10 isin sleep state 2 the three axis accelerometer 42 and the keypad 16 aremonitored to determine if the DCD 10 is moving or if a key on the keypad 16 has been depressed as indicated in decision block 144. If the DCD10 is moved or a key depressed, then the DCD 10 is woken up to allownormal operation, and the timer T1 is reset as indicated in block 146.The state of the DCD 10 then passes to the decision block 130.

If the DCD 10 is not lying front down when the test in decision block130 is made, then state of the DCD 10 passes to the decision block 150in FIG. 3B. In decision block 150 the three axis accelerometer 42detects if the DCD 10 has been put back down. If not then the flow chartof FIG. 3B branches to letter C which continues in FIG. 3C. If the DCD10 is lying back down then a second timer T2 is started as shown inblock 152. The timer T2 may be implemented by starting the timer with apredetermined time, and once started, decremented until the timer T2times out by reaching zero. After the timer T2 has started the threeaxis accelerometer 42, the keypad 16, and the phone in the DCD 10 aremonitored to detect if the DCD 10 is moving, whether a key on the keypad16 is depressed, or whether the phone in the DCD is in use in decisionblock 154. If none of these events has occurred, then the timer T2 ischecked to see if it has timed out in decision block 156. If not thenthe state of the DCD 10 passes to the decision block 154. Thus the threeaxis accelerometer 42, the keypad 16, and the phone in the DCD 10 aremonitored to detect if the DCD 10 is moving, whether a key on the keypad16 is depressed, or whether the phone in the DCD is in use during thetime that the timer T2 is operating.

If, during the period of time that the DCD 10 is monitoring the threeaxis accelerometer 42, the keypad 16, and the use of the phone in theDCD 10 in decision block 136, if the DCD 10 is moved, a key on thekeypad 16 is depressed, or the phone in the DCD is in use, then timer T2is reset in block 158, and the state of the DCD 10 passes from block 158to decision block 130 in FIG. 3A.

If the timer T2 has timed out in decision block 156, then the DCD 10will enter sleep state 3 as indicated in block 160. Once the DCD 10 isin sleep state 3 the three axis accelerometer 42 and the keypad 16 aremonitored to determine if the DCD 10 is moving or if a key on the keypad 16 has been depressed as indicated in decision block 162. If the DCD10 is moved or a key depressed, then the DCD 10 is woken up to allownormal operation, and the timer T2 is reset as indicated in block 164.The state of the DCD 10 then passes to the decision block 130 in FIG.3A.

If the DCD 10 is not lying back down when the test in decision block 150is made, then the state of the DCD 10 passes to the decision block 170in FIG. 3C. In decision block 170 the three axis accelerometer 42, thekeypad 16, and the phone in the DCD 10 are monitored to detect if theDCD 10 is moving, whether a key on the keypad 16 is depressed, orwhether the phone in the DCD is in use. If the DCD 10 is moving, a keyon the keypad 16 is depressed, or the phone in the DCD is in use, thenthe flow chart of FIG. 3C branches to decision block 130 in FIG. 3A. Ifthe DCD 10 is not moving, if none of the keys on the keypad 16 isdepressed, and if the phone in the DCD is not in use, then a third timerT3 is started as shown in block 172. The timer T3 may be implemented bystarting the timer with a predetermined time, and once started,decremented until the timer T3 times out by reaching zero. After thetimer T3 has started the three axis accelerometer 42, the keypad 16, andthe phone in the DCD 10 are monitored to detect if the DCD 10 is moving,whether a key on the keypad 16 is depressed, or whether the phone in theDCD is in use in decision block 174. If none of these events hasoccurred, then the timer T3 is checked to see if it has timed out indecision block 176. If not then the state of the DCD 10 passes to thedecision block 174. Thus the three axis accelerometer 42, the keypad 16,and the phone in the DCD 10 are monitored to detect if the DCD 10 ismoving, whether a key on the keypad 16 is depressed, or whether thephone in the DCD is in use during the time that the timer T3 isoperating.

If, during the period of time that the DCD 10 is monitoring the threeaxis accelerometer 42, the keypad 16, and the use of the phone in theDCD 10 in decision block 136, if the DCD 10 is moved, a key on thekeypad 16 is depressed, or the phone in the DCD is in use, then timer T3is reset in block 158, and the state of the DCD 10 passes from block 158to decision block 130 in FIG. 3A.

If the timer T3 has timed out in decision block 176, then the DCD 10will enter sleep state 4 as indicated in block 180. Once the DCD 10 isin sleep state 4 the three axis accelerometer 42 and the keypad 16 aremonitored to determine if the DCD 10 is moving or if a key on the keypad 16 has been depressed as indicated in decision block 182. If the DCD10 is moved or a key depressed, then the DCD 10 is woken up to allownormal operation, and the timer T3 is reset as indicated in block 184.The state of the DCD 10 then passes to the decision block 130 in FIG.3A.

By way of example, the DCD 10 may be put front down and enter into sleepstate 1, and, after the timer T1 has timed out, enter sleep state 2.Then, after the DCD 10 has been used, the DCD 10 may be put back downand, after timer T2 has timed out, enter sleep state 3. Then after theDCD 10 has been used again, the DCD 10 may be put in a position which isneither front down or back dawn, and, after timer T3 has timed out,enter into sleep state 4.

Although the timers T1, T2, and T3 are shown and described as separatetimers, one or two timers may be used for timers T1, T2, and T3.Similarly, although the sleep states 2, 3, and 4 are shown and describedas separate sleep states, one or two sleep states may be used for sleepstates 2, 3, and 4.

The time out times of the timers T1, T2, and T3 is made considering thepower to be saved and whether a user would find the time out times soshort as to be a nuisance. For example a time out time which is shortenough to put the DCD 10 in a sleep state when a user puts the DCD 10down long enough to move a package would be an inconvenience to the usersince the user would have to wait for the DCD 10 to wake up. In additionto the sleep times shown in FIGS. 3A, 3B, and 3C, the operating systemsoftware used in the DCD 10 may include an inactivity timer that putsthe DCD 10 into a sleep state when the operating system detects thatthere has not been any activity for a predetermined time. For example,the operating system might have an inactivity timer set for 10 minutes,while the time T1 may be set for one minute, the timer T2 set for 5minutes, and the timer T3 set for 8 minutes. Thus if the DCD 10 is notused while in a moving vehicle the operating system inactivity timerwould put the DCD 10 in a sleep state after 10 minutes.

FIG. 4 is a flow chart showing another process for power managementwhich may be used with the DCD 10. FIG. 4 also shows a process forautomatically switching the DCD phone between handset mode andspeakerphone mode. The process shown in FIG. 4 begins when the DCD 10phone is turned on as indicated by circle 190. When the DCD 10 phone isturned on the proximity sensor portion of the combination ambient lightsensor and proximity sensor 22 is enabled. The proximity sensor portionincludes the LED 24 and the combination photodiode array and opticalfilter 28. Since the LED 24 draws a not insignificant amount of currentwhen turned on, it may only be enabled when the DCD 10 phone is in use,and the proximity portion may be turned on and off periodically when theDCD 10 phone is in use to further conserve power in the DCD 10.

After the proximity detection portion is enabled, a determination ismade in decision block 194 whether the DCD 10 is close to a user's faceas generally would be the case if the DCD 10 phone was used as ahandset. If the DCD 10 phone is not close to a user's face, the DCD 10is then switched to the speakerphone mode if it was in the handset modebefore as shown in block 196. In which case the handset speaker 94 wouldbe disabled and the speakerphone speaker 30 would be enabled. Then theproximity detector portion is used again to determine if the DCD 10 isclose to a user's face in decision block 194.

If the proximity detection portion determines that the phone is close toa user's face, then the DCD 10 phone is switched to the handset mode ifit was in the speakerphone mode before as shown in block 198 to disablethe speakerphone speaker 30 and enable the handset speaker 94. Then thepower to the display 18, the touch sensitive panel 20, and the keypadlight 90 is turned off. The power to the touch panel 20 is turned off tonot only save power but to also prevent the DCD 10 from performing anunwanted operation caused by the touch sensitive panel 20 touching auser's cheek while the user is using the phone in the handset mode. Thenthe proximity detector portion is used again to determine if the DCD 10is close to a user's face in decision block 194.

The threshold set for the proximity detector for determining if the DCD10 is close to a user's face depends of the infrared reflectance of auser's face, the color of a user's hair, etc.

FIG. 5 is a side view of another DCD 300 according to another embodimentof the present invention. The DCD 300 may be the DCD 10 with a handle302 attached. The handle does not allow the DCD 300 to be put down onits back side, but instead may be put down leaning on a side edge of theDCD 10 and the end of the handle 302.

FIG. 6 is a flow chart showing a process for power management which maybe used with the DCD 300. FIG. 6 is FIG. 3B with decision block 310substituted for decision block 150 in FIG. 3B. Thus the software used todetect if the DCD 10 in back side down in the process shown in FIG. 3Bwould be modified to recognize that either of the two leaning positionsof the DCD 300 is equivalent to the DCD 10 lying back down. In some usesof the DCD 300 the DCD 300 may often be stored in another orientationsuch as with the top edge facing down as when the DCD 300 is storedbetween a handle on a cart and an edge of the cart. The software couldbe modified to recognize this orientation as equivalent to the DCD 10lying back down.

While the invention has been described with reference to particularembodiments, it will be understood by those skilled in the art thatvarious changes may be made and equivalents may be substituted forelements thereof without departing from the scope of the invention. Inaddition, many modifications may be made to adapt a particular situationor material to the teachings of the invention without departing from thescope of the invention.

Therefore, it is intended that the invention not be limited to theparticular embodiments disclosed as the best mode contemplated forcarrying out this invention, but that the invention will include allembodiments falling within the scope and spirit of the appended claims.

1. A device, comprising: a main body having a front and a back; a touchscreen on the front of the main body; an accelerometer within the mainbody for detecting movement and an orientation of the device; and aprocessor within the main body configured for: determining if the deviceis front down or back down; if the device is front down, placing thedevice in a first sleep state and then a second sleep state based on atime elapsed without detecting movement of the device or receivinginput; if the device is back down, placing the device in a third sleepstate based on a time elapsed without detecting movement of the deviceor receiving input; and if the device is neither front down nor backdown, placing the device in a fourth sleep state based on a time elapsedwithout detecting movement of the device or receiving input.
 2. Thedevice of claim 1, comprising a proximity sensor within the main bodyfor detecting the device's proximity to other objects, wherein theprocessor is configured for placing the device in a reduced power statein response to detecting, with the proximity sensor, that the device isclose to a user's face.
 3. The device of claim 1, wherein the processoris configured for, when the device is front down, placing the device inthe second sleep state after a first predetermined time period in thefirst sleep state.
 4. The device of claim 1, wherein the processor isconfigured for, when the device is back down, placing the device in thefourth sleep state after a second predetermined time period in the thirdsleep state.
 5. The device of claim 1, wherein the processor isconfigured for, when the device is neither front down nor back down,placing the device in the fourth sleep state after a third predeterminedtime period.
 6. The device of claim 1, wherein: the processor isconfigured for, when the device is front down, placing the device in thesecond sleep state after a first predetermined time period in the firstsleep state; the processor is configured for, when the device is backdown, placing the device in the fourth sleep state after a secondpredetermined time period in the third sleep state; the processor isconfigured for, when the device is neither front down nor back down,placing the device in the fourth sleep state after a third predeterminedtime period; the second predetermined time period is longer than thefirst predetermined time period; and the third predetermined time periodis longer than the second predetermined time period.
 7. The device ofclaim 1, wherein the processor is configured for turning off the touchscreen when placing the device in the first sleep state.
 8. The deviceof claim 1, wherein the processor is configured for turning off thetouch screen when placing the device in the first sleep state.
 9. Thedevice of claim 1, wherein the processor is configured for inactivatingmore device functions in the third sleep state than in the first sleepstate.
 10. The device of claim 1, wherein the processor is configuredfor inactivating more device components in the third sleep state than inthe first sleep state.
 11. A system, comprising: a device, comprising: amain body having a front and a back; a touch screen on the front of themain body; an accelerometer within the main body for detecting movementand an orientation of the device; and a processor configured for:determining if the device is front down or back down; if the device isfront down, placing the device in a first sleep state and then a secondsleep state based on a time elapsed without detecting movement of thedevice or receiving input since the device was placed in the first sleepstate; if the device is back down, placing the device in a third sleepstate based on a time elapsed without detecting movement of the deviceor receiving input; and if the device is neither front down nor backdown, placing the device in a fourth sleep state based on a time elapsedwithout detecting movement of the device or receiving input.
 12. Thesystem of claim 11, comprising a proximity sensor within the main bodyfor detecting the device's proximity to other objects, wherein theprocessor is configured for placing the device in a reduced power statein response to detecting, with the proximity sensor, that the device isclose to a user's face.
 13. The system of claim 11, wherein theprocessor is configured for, when the device is front down, placing thedevice in the second sleep state after a first predetermined time periodin the first sleep state.
 14. The system of claim 11, wherein theprocessor is configured for, when the device is back down, placing thedevice in the fourth sleep state after a second predetermined timeperiod in the third sleep state.
 15. The system of claim 11, wherein theprocessor is configured for, when the device is neither front down norback down, placing the device in the fourth sleep state after a thirdpredetermined time period.
 16. The system of claim 11, wherein theprocessor is configured for turning off the touch screen when placingthe device in the first sleep state.
 17. A device, comprising: a mainbody having a front and a back; a touch screen on the front of the mainbody; an accelerometer within the main body for detecting movement andan orientation of the device; and a processor within the main bodyconfigured for: determining if the device is front down or back down; ifthe device is front down, placing the device in a first sleep state andthen a second sleep state based on a time elapsed without detectingmovement of the device or receiving input since the device was placed inthe first sleep state; and if the device is back down, placing thedevice in a third sleep state based on a time elapsed without detectingmovement of the device or receiving input since the device wasdetermined to be back down.
 18. The device of claim 17, wherein theprocessor is configured for, when the device is neither front down norback down, placing the device in a fourth sleep state based on a timeelapsed without detecting movement of the device or receiving input. 19.The device of claim 17, wherein the processor is configured for turningoff the touch screen when placing the device in the first sleep state.20. The device of claim 17, wherein the processor is configured forinactivating more device functions in the third sleep state than in thefirst sleep state.